Conversation
📝 WalkthroughWalkthroughBuild and publish configuration adjusted: Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📜 Recent review detailsConfiguration used: defaults Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
✏️ Tip: You can disable this entire section by setting Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
package.json (1)
17-18:npm_packscript path is stale and will fail.The
npm_packscript still referencesdist/angular-shepherd, but the ng-packagr output now goes toprojects/shepherd/dist/. Thepackagescript will fail.🔧 Suggested fix
- "npm_pack": "cd dist/angular-shepherd && npm pack", + "npm_pack": "cd projects/shepherd/dist && npm pack",
🤖 Fix all issues with AI agents
In `@projects/shepherd/ng-package.json`:
- Line 3: The npm_pack script in the root package.json references the old output
path "cd dist/angular-shepherd" which no longer matches the ng-package.json dest
set to "dist" (outputting to projects/shepherd/dist/); update the npm_pack
script to cd into the new compiled folder (adjust the path to
projects/shepherd/dist/angular-shepherd or if the package is now directly under
projects/shepherd/dist, change to cd projects/shepherd/dist) and ensure
subsequent tar or npm pack commands target that corrected directory so the
package script can find the build output.
In `@projects/shepherd/package.json`:
- Around line 29-34: The package will publish a top-level dist/ folder which
breaks imports; restore the previous publish behavior by either re-adding
publishConfig.directory with the exact value publishConfig.directory:
"../../dist/angular-shepherd" so the built package contents are published at the
package root (correct for ng-packagr), or change the build/publish workflow
invoked by release-plan publish to output build artifacts directly into dist/
(removing the nested angular-shepherd subdir) and keep files: ["dist"]; update
the package.json to use the chosen approach so consumers import from
angular-shepherd as before.
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (5)
.gitignorepackage.jsonprojects/shepherd/README.mdprojects/shepherd/ng-package.jsonprojects/shepherd/package.json
💤 Files with no reviewable changes (1)
- projects/shepherd/README.md
🔇 Additional comments (2)
.gitignore (1)
4-4: LGTM!The pattern change from
/disttodistcorrectly ignores dist directories at any level, which aligns with the new build output location atprojects/shepherd/dist/.package.json (1)
13-13: Build script correctly updated.The
build_libscript now copiesREADME.mdto the correct output location atprojects/shepherd/dist/.
✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.
| { | ||
| "$schema": "../../node_modules/ng-packagr/ng-package.schema.json", | ||
| "dest": "../../dist/angular-shepherd", | ||
| "dest": "dist", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat projects/shepherd/ng-package.jsonRepository: shipshapecode/angular-shepherd
Length of output: 295
🏁 Script executed:
cat package.json | jq '.scripts.npm_pack' 2>/dev/null || cat package.json | grep -A 5 '"npm_pack"'Repository: shipshapecode/angular-shepherd
Length of output: 112
Fix misaligned output path in npm_pack script.
The dest in projects/shepherd/ng-package.json is now "dist" (resolving to projects/shepherd/dist/), but the root package.json npm_pack script still references cd dist/angular-shepherd. This mismatch will break the package script when it tries to locate the compiled output.
Update the npm_pack script to use the correct path that aligns with the new destination.
🤖 Prompt for AI Agents
In `@projects/shepherd/ng-package.json` at line 3, The npm_pack script in the root
package.json references the old output path "cd dist/angular-shepherd" which no
longer matches the ng-package.json dest set to "dist" (outputting to
projects/shepherd/dist/); update the npm_pack script to cd into the new compiled
folder (adjust the path to projects/shepherd/dist/angular-shepherd or if the
package is now directly under projects/shepherd/dist, change to cd
projects/shepherd/dist) and ensure subsequent tar or npm pack commands target
that corrected directory so the package script can find the build output.
Summary by CodeRabbit
Chores
Packaging
Documentation
✏️ Tip: You can customize this high-level summary in your review settings.